-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only fetch HIR for naked functions that have the attribute. #98489
Conversation
r? @davidtwco (rust-highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 5edd85c67f8188a9e7e5e6ca30e22ed575563eaf with merge fab3c552e0ea0923e7f6fed2f41ccca140d2e9d5... |
This comment has been minimized.
This comment has been minimized.
☀️ Try build successful - checks-actions |
Queued fab3c552e0ea0923e7f6fed2f41ccca140d2e9d5 with parent 1aabd8a, future comparison URL. |
Finished benchmarking commit (fab3c552e0ea0923e7f6fed2f41ccca140d2e9d5): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Footnotes |
☔ The latest upstream changes (presumably #98222) made this pull request unmergeable. Please resolve the merge conflicts. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good to me, but this was presumably an attempt to improve perf?
☔ The latest upstream changes (presumably #99024) made this pull request unmergeable. Please resolve the merge conflicts. |
@cjgillot what's the current status here? is this waiting on anything from me? |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 6eb0c89 with merge ce46a33fcef390841f07ef957ca8e2182a755d0f... |
☀️ Try build successful - checks-actions |
Queued ce46a33fcef390841f07ef957ca8e2182a755d0f with parent 04f72f9, future comparison URL. |
Finished benchmarking commit (ce46a33fcef390841f07ef957ca8e2182a755d0f): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Footnotes |
@davidtwco this was initially an attempt to improve perf. In the end, this is only a simplification without any perf regression, so I think it's still worth being merged. |
Thanks. @bors r=davidtwco,tmiasko |
☀️ Test successful - checks-actions |
Finished benchmarking commit (9b8cfc1): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
No description provided.